Due Diligence in Mortgage Documents

ABSTRACT

Due diligence of mortgage documents is faster and simpler. An electronic mortgage application often contains or references a collection of many separate electronic mortgage documents. Electronic data representing an original version of an electronic mortgage document and its current version may be hashed to generate digital signatures. Any auditor may then quickly conduct the due diligence by comparing the digital signatures. If the digital signatures match, then the due diligence reveals that the electronic mortgage document has not changed since its creation. However, if the digital signatures do not match, then the electronic mortgage document has changed since its creation. The auditor may thus flag the electronic mortgage document for additional due diligence. Regardless, a result of the due diligence may be incorporated into one or more blockchains.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application relates to U.S. application Ser. No. 15/419,033 filedJan. 30, 2017, to U.S. application Ser. No. 15/419,042 filed Jan. 30,2017, to U.S. application Ser. No. 15/435,612 filed Feb. 17, 2017, toU.S. application Ser. No. 15/452,760 filed Mar. 8, 2017, to U.S.application Ser. No. 15/456,067 filed Mar. 10, 2017, to U.S. applicationSer. No. 15/459,061 filed Mar. 15, 2017, and to U.S. application Ser.No. ______ filed ______ [Attorney Document Factom #7], with allapplications incorporated herein by reference in their entireties.

BACKGROUND

The mortgage industry has learned from the past. The so-called mortgagecrisis of 2007 exposed flaws in the mortgage industry. Many mortgageslacked sufficient documentation, checks and balances were notimplemented, and fraud was alleged.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The features, aspects, and advantages of the exemplary embodiments areunderstood when the following Detailed Description is read withreference to the accompanying drawings, wherein:

FIGS. 1-8 are simplified illustrations of conducting a due diligence,according to exemplary embodiments;

FIGS. 9-10 are detailed illustration of an operating environment,according to exemplary embodiments;

FIGS. 11-12 illustrate metadata, according to exemplary embodiments;

FIG. 13 illustrates structured data, according to exemplary embodiments;

FIG. 14 illustrates instructions, according to exemplary embodiments;

FIG. 15 illustrates common loan data, according to exemplaryembodiments;

FIG. 16 illustrates a timing requirement, according to exemplaryembodiments;

FIG. 17 illustrates an index, according to exemplary embodiments;

FIGS. 18-20 illustrate sourcing, according to exemplary embodiments;

FIG. 21 illustrates document retrieval, according to exemplaryembodiments;

FIG. 22 further illustrates the due diligence, according to exemplaryembodiments;

FIG. 23 illustrates publication of a due diligence file, according toexemplary embodiments;

FIGS. 24-25 illustrate secret sharing of the due diligence file,according to exemplary embodiments;

FIGS. 21-22 illustrate secret sharing of the due diligence file,according to exemplary embodiments;

FIGS. 23-24 illustrate a sharing strategy, according to exemplaryembodiments;

FIGS. 26-27 illustrate a sharing strategy, according to exemplaryembodiments;

FIG. 28 further illustrates the sharing strategy, according to exemplaryembodiments;

FIG. 29 is a flowchart illustrating a method or algorithm for conductingthe due diligence, according to exemplary embodiments; and

FIGS. 30-31 depict still more operating environments for additionalaspects of the exemplary embodiments.

DETAILED DESCRIPTION

The exemplary embodiments will now be described more fully hereinafterwith reference to the accompanying drawings. The exemplary embodimentsmay, however, be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Theseembodiments are provided so that this disclosure will be thorough andcomplete and will fully convey the exemplary embodiments to those ofordinary skill in the art. Moreover, all statements herein recitingembodiments, as well as specific examples thereof, are intended toencompass both structural and functional equivalents thereof.Additionally, it is intended that such equivalents include bothcurrently known equivalents as well as equivalents developed in thefuture (i.e., any elements developed that perform the same function,regardless of structure).

Thus, for example, it will be appreciated by those of ordinary skill inthe art that the diagrams, schematics, illustrations, and the likerepresent conceptual views or processes illustrating the exemplaryembodiments. The functions of the various elements shown in the figuresmay be provided through the use of dedicated hardware as well ashardware capable of executing associated software. Those of ordinaryskill in the art further understand that the exemplary hardware,software, processes, methods, and/or operating systems described hereinare for illustrative purposes and, thus, are not intended to be limitedto any particular named manufacturer.

As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless expressly stated otherwise. Itwill be further understood that the terms “includes,” “comprises,”“including,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. It will be understood thatwhen an element is referred to as being “connected” or “coupled” toanother element, it can be directly connected or coupled to the otherelement or intervening elements may be present. Furthermore, “connected”or “coupled” as used herein may include wirelessly connected or coupled.As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first device could be termed asecond device, and, similarly, a second device could be termed a firstdevice without departing from the teachings of the disclosure.

FIGS. 1-8 are simplified illustrations of conducting a due diligence 20,according to exemplary embodiments. While the due diligence 20 may beperformed for any legal, financial, or technical purpose, thisdisclosure will mainly describe the due diligence 20 for the mortgageindustry. That is, FIG. 1 illustrates a server 22 storing electronicdata 24 representing one or more electronic mortgage documents 26. Theelectronic mortgage documents 26 may be a part or a component of one ormore loan applications 30. Indeed, many readers are likely familiar withan electronic mortgage application 30 that is processed when financing amortgage for a home or business property. The electronic data 24,however, may be associated with any other type of loan, such as avehicle installment, business or equipment purchase, and even equitylines of credit. The electronic data 24 may also be associated withmortgage backed securities, collateralized mortgage obligations,collateralized debt, real estate investment trust, and otherasset-backed investments. Whatever the electronic data 24, the server 22may retrieve the electronic data 24 representing an original version 32of the electronic mortgage documents 26 at their date and time ofcreation 34. The server 22 may then hash the original version 32 of theelectronic mortgage documents 26 using a cryptographic hashing algorithm36. This disclosure defines a cryptographic “audit key” 38 as the hashvalue(s) 40 generated from hashing the original version 32 of theelectronic mortgage documents 26. Exemplary embodiments may generate asingle audit key 38 or multiple audit keys 38, as later paragraphs willexplain.

An auditor 42 thus performs the due diligence 20. As the readerunderstands, financial records are often sampled and evaluated,especially for investment purposes. For example, when the electronicmortgage documents 26 are packaged as asset-backed securities, the duediligence 20 is performed with respect to the disclosure of materialinformation during the purchase and sale of securities and otherfinancial transactions. When the auditor 42 conducts the due diligence20 related to the electronic mortgage documents 26, the server 22generates one or more virtual due diligence files 44. That is, theserver 22 may retrieve the cryptographic audit key(s) 38 generated fromhashing the original version 32 of the electronic mortgage documents 26.The server 22 packages or associates the cryptographic audit key(s) 38to the due diligence file 44 and sends the due diligence file 44 via acommunications network 46 to the auditor 42 for examination,verification, compliance, and/or regulatory review.

FIG. 2 illustrates a due diligence server 50. The due diligence server50 operates on behalf of the auditor 42 (such as a buyer, seller, orgovernmental entity) to perform the due diligence 20. When the duediligence server 50 receives the due diligence file 44, the duediligence 20 may commence. For example, the due diligence server 50 mayretrieve or receive the electronic data 24 representing a currentversion 52 of the electronic mortgage document 26. As the reader mayunderstand, the current version 52 (perhaps as of a current date andtime 54) may different, perhaps only slightly, from the original version32 generated or saved approximately at the creation 34. Any differencebetween the original version 32 and the current version 52 may indicatean unintentional, or intentional, change to the electronic mortgagedocuments 26. Such a slight change is conventionally difficult todiscern, especially by human inspection.

Exemplary embodiments, though, automate the due diligence 20. Exemplaryembodiments may compare the cryptographic audit key(s) 38 to the currentversion 52 of the electronic mortgage documents 26. That is, the duediligence server 50 may independently hash the electronic data 24representing the current version 52 of the electronic mortgage documents26 (using the same cryptographic hashing algorithm 36) to generate oneor more verification hash values 56. If the verification hash values 56match the cryptographic audit keys 38 sent via the due diligence file44, then the electronic mortgage document 26 has not changed since thedate and time of creation 34. That is, the current version 52 of theelectronic mortgage documents 26 is the same as the original version 32,unaltered, and thus authentic 58. However, if the verification hashvalues 56 (generated from hashing the current version 52 of theelectronic mortgage documents 26) fail to match the cryptographic auditkeys 38 incorporated into the due diligence file 44, then the electronicmortgage documents 26 have changed since the date and time of creation34. The due diligence file 44, in other words, reveals an alterationthat may indicate the current version 52 is inauthentic 60. Exemplaryembodiments may thus generate a flag 62 or other alert 64 to initiatefurther due diligence investigation.

FIG. 3 further illustrates the due diligence 20. The due diligenceserver 50 inspects the data or information contained within, and/orreferenced by, the due diligence file 44 to conduct the due diligence20. The due diligence server 50 generates a result 70 of the duediligence 20. The result 70 may be as simple or as complicated asneeded. For example, the result 70 of the due diligence 20 may be arating 72. The rating 72 is usually with reference to some minimum ormaximum value or scale. The rating 72 may be some grade or evaluationassigned by a rating agency 74 or other third party entity. The result70 of the due diligence 20 may additionally or alternatively be afinancial value 76. The result 70 may be incorporated into the duediligence file 44, or the result 70 may be separate data or information.

FIG. 4 further illustrates the due diligence file 44. As the duediligence server 50 performs the due diligence 20, the due diligenceserver 50 may augment the due diligence file 44. The due diligenceserver 50, for example, may add metadata or information describing apurpose 78 and scope 80 of the due diligence 20 at a date/time 82. Thepurpose 78 of the due diligence 20 may describe why the electronicmortgage documents 26 were audited or reviewed, such as describing abuyer/seller, broker/dealer, the party conducting the due diligence 20,a transaction or acquisition, transaction terms, and the result 70. Thescope 80 may describe the collateral, the mortgage documents 26reviewed, process and policies applied, valuation methodology,representations and warranties, and even indemnification. The duediligence file 44 may further include data describing any exceptions 84to the due diligence 20, such as practice areas or procedures notreviewed or audited. Indeed, the due diligence file 44 may includetracking information (or tracking “info”) 84 related to the exceptions86, thus allowing future due diligence efforts to be calendared andscheduled for follow-up action. The due diligence file 44 may furtherinclude data describing resolutions 88 that resolve or modify theexceptions 86. The due diligence file 44, in other words, may includedue diligence data 90 generated prior to performing the due diligence20, generated during performance of the due diligence 20, and generatedafter performing the due diligence 20.

FIG. 5 illustrates due diligence records. Here exemplary embodiments mayrecord the due diligence 20 as a record in a blockchain 100. As thereader may understand, the blockchain 100 is generally a digital ledgerin which transactions are chronologically and/or publically recorded.The blockchain 100 is most commonly used in decentralizedcryptocurrencies (such as Bitcoin). The blockchain 100, however, may beadapted to any chain or custody (such as the due diligence 20 conductedon the electronic mortgage document(s) 26). Indeed, there are manydifferent mechanisms and configurations of the blockchain 100, andexemplary embodiments may be adapted to any version. Regardless, the duediligence server 50 may integrate the due diligence 20 into theblockchain 100 for distribution or publication to other devices 102.That is, the data representing the due diligence file 44 and/or theresult 70 may be recorded in the blockchain 100 for historicaldocumentation and reference. The due diligence server 50 mayadditionally or alternatively hash any of the due diligence file 44and/or the result 70 (using the hashing algorithm 36) and integrate thedigital signatures into the blockchain 100. The blockchain 100 thusprovides a publication mechanism for tracking the due diligence 20 ofthe electronic mortgage document(s) 24. The due diligence 20 may thus bearchived and accessed for future efforts that validate or verify theelectronic mortgage document(s) 24.

FIG. 6 further illustrates publication. Here exemplary embodiments maydistribute the due diligence file 20 via the blockchain 100. When theserver 22 creates the due diligence file 20, the server 22 mayincorporate the due diligence file 44 as a record in the blockchain 100for historical documentation and reference. The blockchain 100 may thusinclude any cryptographic hash values or digital signatures generatedfrom the due diligence file 44 (such as the audit key(s) 38). While theserver 22 may send the blockchain 100 to any destination address, FIG. 6illustrates the due diligence server 50. That is, the due diligenceserver 50 may be a recipient of the blockchain 100. Because theblockchain 100 may contain the raw electronic data 24, the due diligencefile 44, and/or their corresponding hash value(s) (such as the auditkey(s) 38), the blockchain 100 may archive the informational basis forthe due diligence 20.

Exemplary embodiments thus present elegant due diligence tools.Exemplary embodiments provide a cryptographic mechanism for conductingthe due diligence 20 of the electronic mortgage documents 26. The entityconducting the due diligence 20 need only retrieve and hash the currentversion 52 and compare to the audit key(s) 38 (described by the duediligence file 44). If the digital signatures substantially or exactlymatch, then perhaps the due diligence 20 is complete and no furtherinvestigation is required. But if the current version 52 has changed,the digital signatures will differ, perhaps even substantially. Indeed,even a change to a single character in a single word can produce anoticeable difference in hash values. So, if the digital signatures aredifferent, the current version 52 of the electronic mortgage documents26 may fail an authentication (e.g., the authentic 58 or inauthentic 60determination). The auditor 42 may thus simply and quickly discernwhether the electronic mortgage documents 26 require additionalinvestigative scrutiny. The blockchain 100 publically, or privately,archives the due diligence 20 for historical use and analysis.

FIG. 7 further illustrates the due diligence file 44. Here the duediligence file 44 may include any or all of the electronic mortgagedocuments 26 from multiple electronic mortgage applications 30. Becauseexemplary embodiments are particularly useful for auditing securitizedassets, a typical financial product may include hundreds or eventhousands of mortgages. The due diligence file 44 may thus include theelectronic data 24 representing hundreds or thousands of electronicmortgage documents 26 associated with hundreds or thousands ofelectronic mortgage applications 30. These hundreds or thousands ofdocuments are simply too cumbersome to illustrate. FIG. 7 thus simplyillustrates four (4) electronic mortgage applications 30 a-d associatedwith four (4) different properties and/or applicants. The due diligencefile 44 may thus include or reference the electronic data 24 a-drepresenting all the mortgage documents 26 in the four (4) electronicmortgage applications 30 a-d. The server 22 sends the due diligence file44 to the auditor 42 for the due diligence 20. If the due diligenceserver 50 matches any corresponding cryptographic audit key 38 a-d(generated from hashing the original versions 32 a-d) to the currentversions 52 a-d of the electronic mortgage applications 30 a-d, then theelectronic data 24 a-d is unaltered and authentic 58. However, if anyverification hash value 56 a-d fails to match the correspondingcryptographic audit key 38 a-d, then the corresponding electronic data24 a-d has changed since its date and time of creation 34 a-d. Exemplaryembodiments may thus escalate the due diligence 20 for additionalauditing procedures.

FIG. 8 also illustrates the due diligence file 44. Here, though, the duediligence file 44 may only include a subset 110 of the electronicmortgage documents 26 from a collection 112 of multiple electronicmortgage applications 30. Because each electronic mortgage application30 may include many documents and/or hundreds of pages, a full duediligence investigation of each page/document may not be feasible orcost effective. Exemplary embodiments may thus limit the due diligence20 and review or audit only a sample data set. The due diligence file 44may thus contain the electronic data 24 a-d representing a sample of theelectronic mortgage documents 26 contained within, or associated with,multiple and different applicants and/or properties. FIG. 8 thusillustrates another simple example in which the due diligence 20 onlyreviews IRS W-2 statements 114 a-d electronically plucked or sifted fromthe four (4) electronic mortgage applications 30 a-d. That is, the duediligence file 44 may contain the electronic data 24 a-d representingthe IRS W-2 statements 114 a-d copied or isolated from the correspondingelectronic mortgage application 30 a-d. The server 22 sends the duediligence file 44 to the auditor 42 for the due diligence 20. If the duediligence server 50 matches any corresponding cryptographic audit key 38a-d (generated from hashing the original versions 32 a-d of the IRS W-2statements 114 a-d) to the current version 52 a-d, then the electronicdata 24 a-d is unaltered and authentic 58. However, if any verificationhash value 56 a-d fails to match the corresponding cryptographic auditkey 38 a-d, then the corresponding applicant's IRS W-2 statement 114 a-dhas changed since its date and time of creation 34 a-d. Exemplaryembodiments may thus escalate the due diligence 20 for additionalscrutiny.

Exemplary embodiments thus present a simple and effective due diligencemechanism. Cryptographic hashing may be used to make quick due diligencedecisions. If an entity conducting the due diligence 20 matchescryptographic digital signatures representing different versions of theelectronic mortgage documents 26, then perhaps the due diligence 20 iscomplete and no further investigation is required. But if the currentversion 52 has changed, the digital signatures will differ, perhaps evensubstantially. Indeed, even a change to a single character in a singleword can produce a noticeable difference in hash values. So, if thedigital signatures are different, the current version 52 of theelectronic mortgage documents 26 may fail an authentication (e.g., theauthentic 58 or inauthentic 60 determination). The auditor 42 may thussimply and quickly discern whether the electronic mortgage documents 26require additional investigative scrutiny. The auditor 42 may then usethe blockchain 100 to archive the due diligence 20 for historical useand analysis.

Exemplary embodiments may be applied to any electronic document. Mostreaders are thought familiar with mortgage documents. This disclosurethus mainly explains the due diligence 20 of mortgage documents.Exemplary embodiments, though, may be applied to the due diligence 20 ofany electronic data representing any document.

FIGS. 9-10 are detailed illustration of an operating environment,according to exemplary embodiments. FIG. 9 illustrates the server 22communicating with the due diligence server 50 (via the communicationsnetwork 46 illustrated in FIGS. 1 and 5). The server 22 may have aprocessor 120 (e.g., “μP”), application specific integrated circuit(ASIC), or other component that executes a server-side algorithm 122stored in a local memory device 124. The server-side algorithm 122includes instructions, code, and/or programs that cause the server 22 toperform operations, such as hashing the electronic data 24 representingthe original version 32 of the electronic mortgage document 26 (usingthe hashing algorithm 36) to generate the audit key(s) 38 and the duediligence file 44 (as the above paragraphs explained). The server-sidealgorithm 122 may also instruct or cause the server 22 to send the duediligence file 44 to the due diligence server 50. The server-sidealgorithm 122 may also instruct or cause the server 22 to send the duediligence file 44 to any IP address associated with any networkdestination or device.

Exemplary embodiments may use any hashing function. Many readers may befamiliar with the SHA-256 hashing algorithm that generates a 256-bithash value. Exemplary embodiments obtain or retrieve the electronic data24 representing the original version 32. The SHA-256 hashing algorithmacts on the electronic data 24 to generate a 256-bit hash value as thecryptographic audit key 38. The audit key 38 is thus a digital signaturethat uniquely represents the electronic data 24. There are many hashingalgorithms, though, and exemplary embodiments may be adapted to anyhashing algorithm.

FIG. 10 illustrates due diligence instructions. When the auditor 42wishes to perform the due diligence 20, the due diligence server 50 maysend a due diligence request 126. The due diligence request 126 mayinclude data or information that specifies a subject 128 of the duediligence 20. The subject 128 may be broadly or narrowly specified toensnare a single document, a single mortgage application, multipledocuments from the single mortgage application, the single document frommultiple mortgage applications, or multiple documents from the multiplemortgage applications. In general, then, the due diligence request 126may specify a document range identifying the document(s) to be reviewedand/or a property/applicant range identifying names, properties, and/ormortgage application(s) to be audited for the due diligence 20. The duediligence server 50 may have a processor 130 (e.g., “μP”), applicationspecific integrated circuit (ASIC), or other component that executes adiligence-side algorithm 132 stored in a local memory device 134. Thediligence-side algorithm 132 includes instructions, code, and/orprograms that cause the due diligence server 50 to perform operations,such as generating the due diligence request 126 and sending the duediligence request 126 to the IP address associated with the server 22.The server 22 thus generates the due diligence file 44 as a response tothe due diligence request 126. The server 22 and the due diligenceserver 50 may thus cooperate to perform the due diligence 20 of theelectronic mortgage documents 26 based on the due diligence file 44.

Exemplary embodiments may be applied regardless of networkingenvironment. Exemplary embodiments may be easily adapted to stationaryor mobile devices having cellular, wireless fidelity (WI-FI®), nearfield, and/or BLUETOOTH® capability. Exemplary embodiments may beapplied to mobile devices utilizing any portion of the electromagneticspectrum and any signaling standard (such as the IEEE 802 family ofstandards, GSM/CDMA/TDMA or any cellular standard, and/or the ISM band).Exemplary embodiments, however, may be applied to anyprocessor-controlled device operating in the radio-frequency domainand/or the Internet Protocol (IP) domain. Exemplary embodiments may beapplied to any processor-controlled device utilizing a distributedcomputing network, such as the Internet (sometimes alternatively knownas the “World Wide Web”), an intranet, a local-area network (LAN),and/or a wide-area network (WAN). Exemplary embodiments may be appliedto any processor-controlled device utilizing power line technologies, inwhich signals are communicated via electrical wiring. Indeed, exemplaryembodiments may be applied regardless of physical componentry, physicalconfiguration, or communications standard(s).

Exemplary embodiments may utilize any processing component,configuration, or system. Any processor could be multiple processors,which could include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The processor could includea state machine, application specific integrated circuit (ASIC),programmable gate array (PGA) including a Field PGA, or state machine.When any of the processors execute instructions to perform “operations,”this could include the processor performing the operations directlyand/or facilitating, directing, or cooperating with another device orcomponent to perform the operations.

Exemplary embodiments may packetize. The server 22 and the due diligenceserver 50 may have network interfaces to the communications network 46,thus allowing collection and retrieval of information. The informationmay be received as packets of data according to a packet protocol (suchas the Internet Protocol). The packets of data contain bits or bytes ofdata describing the contents, or payload, of a message. A header of eachpacket of data may contain routing information identifying anorigination address and/or a destination address.

FIGS. 11-12 illustrate metadata 140, according to exemplary embodiments.Here the due diligence file 44 may include the electronic metadata 140associated with the electronic mortgage document(s) 26 and/or themortgage application(s) 28. The metadata 140 may describe anydocument(s) contained within, or associated with, the electronicmortgage document(s) 26 and/or the mortgage application(s) 28. Forexample, the metadata 140 may describe the creation 34 (such as{“CreationTime”:“2012-05-07T11:12:32”}). The metadata 140 may describethe applicant, the property, a location (such as GPS information at thecreation 34 or a property address), word/character count, and anabstract describing or summarizing the electronic mortgage document(s)26. The metadata 140 may also include one or more keywords associatedwith any of the electronic mortgage document(s) 26. The metadata 140 mayalso include a file hierarchy where the electronic mortgage document(s)26 is/are stored and/or a network address for retrieval. The networkaddress, for example, may be associated with a source server or othermachine locally or remotely storing the electronic mortgage document(s)26. The metadata 140 may also include structural details, such as filesize, page numbering, chapter organization, and image data. Othermetadata 140 may describe approved users (such as administrator and userpermissions or identities) and digital rights management (or “DRM”). Themetadata 140 may be formatted according to any standard. The duediligence file 44 may thus include any metadata 140 associated with theelectronic mortgage document(s) 26.

FIG. 11 also illustrates sourcing data 144. The sourcing data 144 mayalso be a type of the metadata 140 that is associated with theelectronic mortgage document(s) 26 and/or the mortgage application(s)28. The sourcing data 144 specifies from where the electronic mortgagedocument(s) 26 and/or the mortgage application(s) 28 may be obtained.That is, the sourcing data 144 specifies a network location, address,website, and/or other information associated with a networked device orserver that stores the original version 32 and/or the current version52. The sourcing data 144 may be as simple or detailed as needed to easeaccess. The sourcing data 144, for example, may be defined as[{“Source”:{“Name”: “Wells Fargo System XXX”} {“ID”:“YYY”}, {“AccessLink”:“https://foo.wellsfargo.com”} . . . ] and textually written orencoded as the metadata 140. The sourcing data 144 may thus specify oneor more uniform resource locators (URLs) as website links from where thecorresponding electronic mortgage document 26 (document identifier“ID”:YYY”) may be queried and retrieved. The sourcing data 144, however,may be anonymized, thus not hiding or not revealing the responsiblelender, data owner, or contractor [{“Source”:{“Name”: “Anonymous” },{“ID”:“YYY”}, {“AccessLink”:“https://2690:a280:7751:5507:b93z:59fg:44lp:c55q”} . . . ],perhaps thus merely identifying an IP address. The sourcing data 144 mayalso be redacted to additionally or alternatively conceal the sourcingentity. Regardless, the sourcing data 144 may thus be populated by anoriginator or creator of the electronic mortgage document 26. Thesourcing data 144 may also be populated by an owner of the originalversion 32 and/or the current version 52 (such as lender of contractor).The sourcing data 144 may thus be added to any existing metadata 140 toaccompany the due diligence file 44.

FIG. 11 also illustrates a source key 146. Once the sourcing data 144 isdetermined and/or retrieved, the sourcing data 144 may be hashed usingthe cryptographic hashing algorithm 36 to generate one or morecryptographic source keys 146. The cryptographic source key 146 may thenincorporated into the due diligence file 44, and/or the cryptographicsource key 146 may be distributed via the one or more blockchains 100(as illustrated with reference to FIG. 6). Once any recipient receivesthe due diligence file 44 and/or the cryptographic source key 146, therecipient may reverse lookup the sourcing data 144 to retrieve thecorresponding electronic mortgage document 26. That is, the duediligence server 50 may query a database 148 of keys to convert ortranslate the source key 146 back into its corresponding sourcing data144. Sourcing discovery and retrieval are more fully explained in U.S.application Ser. No. 15/456,067 filed Mar. 10, 2017 and incorporatedherein by reference in its entirety.

Exemplary embodiments thus include more simple due diligence tools.Exemplary embodiments may include the sourcing data 144 in the virtualdue diligence file 44. Exemplary embodiments may also cryptographicallyhash the sourcing data 144 to generate the source key 146 fordistribution via the blockchain(s) 100. Any recipient of the blockchain100 may then simply and quickly convert the source key 146 back into thecorresponding sourcing data 144. The due diligence server 50, forexample, may quickly and easily use a query operation to determine thenetwork source storing any mortgage document. The auditor need onlytranslate the source key 146 to easily retrieve mortgage documents forauditing and due diligence purposes.

FIG. 12 illustrates formatting. Here the electronic data 24 representingthe metadata 140 may describe one or more formats 150. Most readers, forexample, are thought familiar with a portable document format (“PDF”)152, the MICROSOFT® WORD® extensible markup language extension (“docx”)154, and/or the extensible markup language (“XML”) 156. Exemplaryembodiments, though, may be applied to any file formatting and/orspecification. The format 150 may be proprietary, free, unpublished,and/or open. The format 150 may be designed for images, containers,audio, video, text, subtitles, control characters, and encoding schemes.The format 150 may be HTML, vector graphics, source code, text files,syntax, and software programming. Whatever the format 150, exemplaryembodiments may retrieve the electronic data 24 representing the format150 of any electronic mortgage document 26. The due diligence file 44may thus include any metadata 140 associated with the format 150 of theelectronic mortgage document(s) 26.

FIG. 13 illustrates structured data 160, according to exemplaryembodiments. As the reader may understand, the electronic data 24representing the electronic mortgage document 26 may be the structureddata 160. That is, the structured data 160 may be organized (such as anentry 162 or database field 164 in a relational spreadsheet 166 ordatabase 168), contained within a fixed data field 170 or data record172, and/or be addressable via a network or memory address 174. Againreferencing the electronic mortgage document 26, the structured data 160may be organized according to the JavaScript Object Notation (or“JSON”). As the JavaScript Object Notation is a known format forstructuring data, the JSON format need not be explained in detail.Suffice it to say that at least some of the electronic data 24representing the electronic mortgage document 26 and/or the duediligence file 44 may be a JSON document 176 having the structured data160 arranged as fields, formatted according to a JSON schema 178.

Exemplary embodiment may thus incorporate a data version 180 in the duediligence file 44. For example, if the electronic mortgage document 26and/or the due diligence file 44 is the JSON document 176, then the dataversion 180 may be the structured data 160 arranged or formattedaccording to the JSON schema 178. Exemplary embodiments may thusretrieve and incorporate the data version 180 in the due diligence file44.

FIG. 14 illustrates instructions 190, according to exemplaryembodiments. Here the due diligence file 44 may include the instructions190. While exemplary embodiments may be applicable to any instructions,the instructions 190 may be structured (such as executable code),unstructured instructions (such as non-executable commentary lines incode, such as English language “do thing 1, then thing 2, then thing3”). Other instructions 190 may include any messages (such as “When thisdocument is accessed, POST to the URL http://some.target.url”).Exemplary embodiments may thus retrieve and incorporate the instructions190 into the due diligence file 44.

FIG. 15 illustrates common loan data 200, according to exemplaryembodiments. Here the due diligence file 44 may include data orinformation that is common or applicable to each electronic mortgagedocument 26 described, referenced, or included within the due diligencefile 44. For example, each electronic mortgage document 26 may beassociated with the metadata 140 describing a common geographic location(e.g., street, city, state, and/or ZIP). The common loan data 200 mayadditionally or alternatively specify a single or common document orpage (again, such as the IRS W-2 statement 114 included in eachelectronic mortgage application 30, as explained with reference to FIG.8). Similarly, the common loan data 200 may also include or describe afinancial lender (such as WELLS FARGO® or BANK OF AMERICA® offering,evaluating, and/or processing the electronic mortgage applications 30.Whatever the common loan data 200 describes, exemplary embodiments mayincorporate the common loan data 200 into the due diligence file 44.

FIG. 16 illustrates a timing requirement, according to exemplaryembodiments. Here the due diligence file 44 may include data orinformation specifying a due diligence interval 202 of time in which thedue diligence 20 must be commenced and/or completed. The due diligencefile 44 may thus cause the due diligence server 50 to call or invoke atiming mechanism (such as a timer 204) that begins counting up, or down,from an initial time 206 to a final time 208. If the due diligenceinterval 202 of time expires prior to commencement or completion of thedue diligence 20, exemplary embodiments may decline further access to,and/or read usage of, the due diligence file 44. The due diligenceinterval 202 of time may thus be a time box or window that incrementsfrom a date/time of receipt 210, or at date/time of initial read access212, by the due diligence server 50. The due diligence interval 202 oftime may additionally or alternatively increment at a date/time ofsending 214 the due diligence file 44 from the server 22. The duediligence file 44 may have additional configuration options that furtherdefine the access or usage conditions related to the auditing interval202 of time.

FIG. 17 illustrates an index 220, according to exemplary embodiments.Here the due diligence file 44 may include the index 220. The index 220may list or describe any or of all the electronic mortgage documents 26that are included within, or referenced by, the due diligence file 44.Because the due diligence file 44 may contain many different andseparate documents, the index 220 may be provided as a courtesy to theauditor 42 performing the due diligence 20. Indeed, the due diligencerequest 126 (explained with reference to FIG. 10) may even require theindex 220. The index 220 may be generated from the electronic data 24representing the electronic mortgage documents 26. The index 220, forexample, may be generated from the metadata 140 associated with theelectronic mortgage documents 26 and/or the mortgage application(s) 30.The index 220 may be also arranged by topical subject 222, document name224, and/or page number 226 to promote auditing efforts. The index 220may additionally or alternatively be alphabetically arranged 228 to aidhuman search and retrieval. The index 220 may even describe and/orlocate the metadata 140 associated with each electronic mortgagedocument 26. The index 220 may also describe the sourcing data 144specifying the storage/retrieval location for each electronic mortgagedocument 26. When the auditor 42 (such as the due diligence server 50)receives the due diligence file 44, the index 220 permits easy machineor user access to the informational components within the due diligencefile 44.

FIGS. 18-20 illustrate sourcing, according to exemplary embodiments.Here the sourcing data 144 may be used to retrieve the original version32 and/or the current version 52 of the electronic mortgage document 26.When the due diligence server 50 receives the due diligence file 44, thedue diligence file 44 may include or specify the cryptographic sourcekey 146 (as this disclosure above explains). The source key 146 may thusrepresent a unique digital signature generated from hashing the metadata140 describing the sourcing data 144 representing a storage or networklocation. Exemplary embodiments may thus generate the one or more sourcekeys 146 as the hash value(s) generated from hashing the sourcing data144. Once the due diligence server 50 receives the due diligence file44, the due diligence server 50 may thus read and/or retrieve the sourcekey(s) 146 to easily and quickly discover the storage location of thecorresponding original version 32 and/or the current version 52 of theelectronic mortgage document 26. That is, the source key 146 may be usedto reverse lookup the sourcing data 144. The due diligence server 50generates and sends a key query 230 to the network address associatedwith the electronic database 148 of keys. FIG. 18 illustrates a keyserver 232 storing or maintaining the electronic database 148 of keys.The electronic database 148 of keys, however, may be stored atmaintained at any network device or location. The electronic database148 of keys stores entries that electronically associate differentsource keys 146 to their corresponding sourcing data 144. The duediligence server 50 queries the key server 232 (via the communicationsnetwork 46 illustrated in FIGS. 1 and 5) for the source key 146 receivedvia the due diligence file 44. The key server 232 retrieves thecorresponding sourcing data 144 and sends a key response 234 to the duediligence server 50. The key response 234 includes informationdescribing the sourcing data 144 retrieved from the electronic database148 of keys. Exemplary embodiments thus allow the due diligence server50 to translate or convert the source key 146 into its correspondingsourcing data 144.

FIG. 19 further illustrates the electronic database 148 of keys. The keyserver 232 functions to answer queries submitted by authorized clients.That is, the key server 232 executes a query handler application 236that accepts the source key 146 as a query term. The query handlerapplication 236 may then search the electronic database 148 of keys fora matching entry. While the electronic database 148 of keys may have anystructure, FIG. 19 illustrates the electronic database 148 of keys as atable 238 that electronically maps, relates, or associates differentsource keys 146 to their corresponding sourcing data 144. The electronicdatabase 148 of keys may thus be loaded or configured with data orinformation for determining the retrieval locations of mortgagedocuments. If a match is determined, the corresponding sourcing data 144is identified. FIG. 19 illustrates the electronic database 148 of keysas being locally stored in the key server 232, but some of the databaseentries may be dispersed to multiple other devices or locations in thecommunications network (illustrated as reference numeral 46 inillustrated in FIGS. 1 and 5). While FIG. 19 only illustrates a fewentries, in practice the electronic database 148 of keys may containhundreds, thousands, or even millions of entries detailing many mortgagedocuments.

FIG. 20 illustrates database replies. The due diligence server 50queries the electronic database 148 of keys for the source key 146received via the due diligence file 44. The key server 232 retrieves andpackages the corresponding sourcing data 144 as a key response 240. Thekey server 232 sends the key response 240 to the network address (e.g.,IP address) associated with the due diligence server 50.

FIG. 21 illustrates document retrieval, according to exemplaryembodiments. Now that the due diligence server 50 has determined thesourcing data 144 associated with the source key 146, the due diligenceserver 50 may retrieve the corresponding electronic mortgage document26. The due diligence server 50 sends a document query 242 specifyingthe sourcing data 144 to a source server 244. When the source server 244receives the document query 242, the source server 244 retrieves andsends the corresponding electronic mortgage document 26 as a documentresponse 246. The due diligence server 50 has thus obtained theelectronic mortgage document 26 referenced or associated with the duediligence file 44.

Exemplary embodiments may thus be used to retrieve different versions ofthe electronic mortgage document 26. If the due diligence file 44references the source key 146 representing the original version 32 ofthe electronic mortgage document 26, then the due diligence server 50need only query the key server 232 to determine the correspondingsourcing data 144 describing the network location associated with theoriginal version 32. Similarly, if the due diligence file 44 referencesthe source key 146 representing the current version 52 of the electronicmortgage document 26, then the due diligence server 50 need only querythe key server 232 to determine the corresponding sourcing data 144describing the network location associated with the current version 52.Exemplary embodiments may thus hash any of the metadata 140 and includethe resulting hash values in the due diligence file 44.

FIG. 22 further illustrates the due diligence 20, according to exemplaryembodiments. The due diligence server 50 inspects the due diligence file44 to conduct the due diligence 20 and to generate the result 70 (suchas the rating 72 and/or the financial value 76). The due diligenceserver 50 may then incorporate the due diligence file 44 and/or theresult 70 into the one or more blockchains 100 for historical reference.The blockchain(s) 100 may further include the digital signaturesgenerated from hashing any of the mortgage documents 26, the mortgageapplications 30, different data versions (such as the original version32 and/or the current version 52), the metadata 140, the format 150, thestructured data 160, and/or the instructions 190. Exemplary embodimentsmay thus document the due diligence 20 in the blockchain(s) 100 forfuture reference. The blockchain(s) 100 may also include the ancillarydue diligence data 90 generated from performing the due diligence 20,perhaps also the corresponding hash values from hashing the duediligence data 90. All this data may be stored and tracked on theblockchain 100, both for validation/verification, as well as for futureaccess by others (e.g., if the MB S's are processed again, re-ratings,ex post facto audits, etc.).

FIG. 23 illustrates publication of the due diligence file 44, accordingto exemplary embodiments. Here exemplary embodiments may distribute thedue diligence file 44 as a record in the blockchain 100. Exemplaryembodiments, in other words, may integrate the due diligence file 44 asa transaction or block of data in the blockchain 100. FIG. 23illustrates the blockchain 100 being distributed from the server 22 tothe due diligence server 50 for the due diligence 20. As the duediligence server 50 performs or completes the due diligence 20, the duediligence server 50 may augment the blockchain 100 with the result 70and the due diligence data 88 (as explained with reference to FIG. 22).The due diligence server 50 may then further publish the blockchain 100to any recipient (such as a peer device 250). Exemplary embodiments maythus add cryptographic digital signatures that cryptically describe thedue diligence 20. Exemplary embodiments may thus integrate the duediligence 20 as a historical ledger transaction or block in theblockchain 100.

FIGS. 24-25 illustrate secret sharing of the due diligence file 44,according to exemplary embodiments. By now the reader understands thatthe due diligence file 44 may contain sensitive information (such as anapplicant's social security number, income, banking, and other personalinformation). The due diligence file 44, in plain words, may containsecret data 252. If the due diligence file 44 was to fall into the wronghands, the secret data 252 may be nefariously used by a rogue entity.

Exemplary embodiments may thus protect the due diligence file 44. Whenthe server 22 generates the due diligence file 44, the server 22 maysplit the due diligence file 44 into multiple pieces termed shares 254a. The server 22 may then distribute one or more of the shares 254 a viathe blockchain 100 to the Internet Protocol address associated with thedue diligence server 50. Likewise, when the due diligence server 50performs or completes the due diligence 20, the due diligence server 50may split the result 70 and the due diligence data 88 (as explained withreference to FIG. 22) into shares 254 b. The due diligence server 50 maythen augment the blockchain 100 with the shares 254 a and/or 254 brepresenting the result 70 and the due diligence data 88. The duediligence server 50 may then further publish the blockchain 100 to anyrecipient (such as the peer device 250).

FIG. 25 further illustrates secret sharing. Here, though, the server 22may integrate any one or more of the shares 254 a into multipleblockchains 100. While exemplary embodiments may utilize any number ofdifferent blockchains 100, FIG. 25 illustrates a simple example of three(3) blockchains 100 a-c. The blockchains 100 a-c may then be distributedto the same destination or to different destinations. FIG. 25, forexample, illustrates three (3) different groups 260 a-c of destinations,with the due diligence server 50 being one of the recipients. That is,some of the shares 254 a (such as a first subset 262) are integratedinto a first blockchain 100 a and distributed (via the communicationsnetwork 46 illustrated in FIGS. 1 and 5) to a first group 260 a of peerdevices. A second subset 264 of the shares 254 a are integrated into asecond blockchain 100 b and distributed to a second group 260 b of peerdevices. Still more shares 254 a (such as the remaining portion orpieces in a third subset 266) are integrated into a third blockchain 100c and distributed to a third group 260 c of peer devices (illustrated asthe due diligence server 50). Different collections of the shares 254 a,in other words, may be distributed via different blockchains 100 a-c todifferent destinations/devices.

Exemplary embodiments may thus stash the shares 254 a in the multipleblockchains 100 a-c. Because the due diligence file 44 may be split intothe multiple shares 254 a, any one or more recipient devices mustpossess a sufficient minimum number M_(Min) (illustrated as referencenumeral 268) of the shares 254 a before the due diligence file 44 may berecovered. That is, possession of an insufficient number of the shares254 a guarantees that the due diligence file 44 remains unknown andconfidential. So, if the first blockchain 100 a contains less than theM_(Min) 268 of the total shares 254 a, then the first group 260 a ofpeer devices cannot reconstruct the due diligence file 44. Likewise, ifthe second blockchain 100 b and/or the third blockchain 100 c alsocontains less than the M_(Min) 268, the second group 260 b of peerdevices and the third group 260 c of peer devices are also unable toreveal or decipher the due diligence file 44. In other words, no singleone of the multiple blockchains 100 a-c stores the requisite minimumnumber M_(Min) 268 of the shares 254 a to launch a brute-force attack onthe due diligence file 44. Even multiple ones of the blockchains 100 a-cmay be purposefully designed to never exceed the requisite minimumnumber M_(Min) 268 of the shares 254 a, perhaps thus forcing a hacker tocompromise several or all of the blockchains 100 a-c. A rogue attack, insimple words, would have to access and compromise multiple blockchains100 before jeopardizing the due diligence file 44.

Exemplary embodiments thus present another elegant solution. Thesensitive, secret due diligence file 44 may be secretly shared via theone or more blockchains 100 a-c. Even if the blockchains 100 a-c aredispersed to trusted peer devices, the peer devices still cannot discernthe due diligence file 44 until the threshold minimum number M_(Min) 268of the shares 254 a is obtained. Exemplary embodiments thus purposefullyadd a second-layer of protection, beyond merely trusted receipt of theblockchain 100. The trusted peers simply do not have access to the duediligence file 44 until the minimum number M_(Min) 268 of the shares 254a is obtained.

Any secret sharing scheme may be utilized. The reader is perhapsfamiliar with Shamir's Secret Sharing Algorithm, which is a well-knowncryptographic algorithm. Exemplary embodiments may thus divide the duediligence file 44 into unique parts (e.g., the shares 254 a), with eachindividual share 242 a being different from other shares 254 a. However,there are many secret sharing or splitting schemes and algorithms fordistributing a secret, and exemplary embodiments may be appliedregardless of any particular scheme or algorithm.

FIGS. 26-27 illustrate a sharing strategy 270, according to exemplaryembodiments. Here the server-side algorithm 122 may call a sharingalgorithm 272 to retrieve and/or to implement the sharing strategy 270that defines distribution via the multiple blockchains 100 to protectthe due diligence file 44. Suppose, for example, that the total numberN_(S) (illustrated as reference numeral 274) of the shares 254 defines anumber N_(B) (illustrated as reference numeral 276) of the differentblockchains 100. The total number N_(S) 274 of the shares 254 a, inother words, may relate by a ratio to the number N_(B) 276 ofblockchains 100 that must be used. As a simple example, the ratio may be

${\frac{N_{S}}{N_{B}} = {10,000}},$

where the total number N_(S) 274 of the shares 254 a is ten thousand(10,000) times the number N_(B) 266 of blockchains 100 that must beused. Again, as a simple example, if the due diligence file 44 isassociated with one million (1,000,000) shares 254 a, then one hundred(100) different blockchains 100 must be generated and distributed. Thesharing strategy 270, in other words, may set a maximum number N_(Smax)(illustrated as reference numeral 278) of shares 254 a integrated intoany single blockchain 100. The sharing strategy 270, in other words, maythus limit the number of the shares 254 a exposed by any individualblockchain 100.

FIG. 27 further illustrates the sharing strategy 270. Here, though, thenumber N_(B) 276 of blockchains may be based on the number ofrecipients. That is, the total number N_(R) (illustrated as referencenumeral 280) of the recipients may define the number N_(B) 276 of thedifferent blockchains 100. The greater the recipients, in other words,then the greater the N_(B) 276 of blockchains 100 that must be used.Again, suppose that the sharing strategy 270 may again be defined as theratio

${\frac{N_{R}}{N_{B}} = 100},$

where the total number N_(R) 280 of the recipients is one hundred (100)times the number N_(B) 276 of blockchains 100 that must be used. Again,as a simple example, if there are ten thousand recipients, then onehundred (100) different blockchains 100 must be generated anddistributed. The sharing strategy 270, in other words, may set a maximumnumber N_(Rmax) (illustrated as reference numeral 282) of recipients perblockchain 100. The sharing strategy 270, in other words, may thus limitthe number of the shares 254 a exposed by any individual blockchain 100.

FIG. 28 further illustrates the sharing strategy 270, according toexemplary embodiments. Here the sharing strategy 270 may be implementedby the due diligence server 50. As the due diligence server 50 performsthe due diligence 20, the diligence-side algorithm 132 may call thesharing algorithm 272 and split the due diligence file 44, the result70, and/or the due diligence data 88 (as explained with reference toFIG. 22) into the shares 254 b according to the sharing strategy 270.That is, exemplary embodiments may define, determine, or calculate thetotal number N_(S) 274 of the shares 254 b, the number N_(B) 276 of thedifferent blockchains 100, the maximum number N_(Smax) 278 of the shares254 b integrated into any single blockchain 100, the total number N_(R)280, and/or the maximum number N_(Rmax) 282 of recipients per blockchain100. The sharing strategy 270, in other words, may thus limit the numberof the shares 254 b exposed by any individual blockchain 100.

The sharing strategy 270 may be implemented as logical rules. If thesharing strategy 270 is mathematically defined (such as the ratio abovediscussed), the sharing strategy 270 may be expressed as logicalstatements involving mathematical expressions. Exemplary embodiments maycode or program the sharing strategy 270 to achieve policy goals and/orsecurity objectives.

FIG. 29 is a flowchart illustrating a method or algorithm for conductingthe due diligence 20 of the electronic mortgage documents 26, accordingto exemplary embodiments. The electronic data 24 representing themortgage document 26 is received (Block 290). The electronic data 24 ishashed using the cryptographic hashing algorithm 36 (Block 292) togenerate the audit key(s) 38 (Block 294). The due diligence file 44 isgenerated (Block 296). If secret sharing is desired (Block 298), thenthe due diligence file 44 is split into the shares 254 a (Block 300). Ifsecure distribution is desired (Block 302), then the due diligence file44 and/or the shares 254 a are published via the blockchain(s) 100(Block 304). The auditor 42 receives the due diligence file 44 (Block306) and conducts the due diligence 20 (as this disclosure explains)(Block 308). The due diligence 20 is then integrated into theblockchain(s) 100 (Block 310).

FIG. 30 is a schematic illustrating still more exemplary embodiments.FIG. 30 is a more detailed diagram illustrating a processor-controlleddevice 350. As earlier paragraphs explained, the server-side algorithm122 and the diligence-side algorithm 132 may partially or entirelyoperate in any mobile or stationary processor-controlled device. FIG.30, then, illustrates the server-side algorithm 122 and thediligence-side algorithm 132 stored in a memory subsystem of theprocessor-controlled device 350. One or more processors communicate withthe memory subsystem and execute either, some, or all applications.Because the processor-controlled device 350 is well known to those ofordinary skill in the art, no further explanation is needed.

FIG. 31 depicts other possible operating environments for additionalaspects of the exemplary embodiments. FIG. 31 illustrates theserver-side algorithm 122 and the diligence-side algorithm 132 operatingwithin various other processor-controlled devices 350. FIG. 31, forexample, illustrates that the server-side algorithm 122 and thediligence-side algorithm 132 may entirely or partially operate within aset-top box (“STB”) (352), a personal/digital video recorder (PVR/DVR)354, a Global Positioning System (GPS) device 356, an interactivetelevision 358, a tablet computer 360, or any computer system,communications device, or processor-controlled device utilizing any ofthe processors above described and/or a digital signal processor(DP/DSP) 362. Moreover, the processor-controlled device 350 may alsoinclude wearable devices (such as watches), radios, vehicle electronics,clocks, printers, gateways, mobile/implantable medical devices, andother apparatuses and systems. Because the architecture and operatingprinciples of the various devices 350 are well known, the hardware andsoftware componentry of the various devices 350 are not further shownand described.

Exemplary embodiments may be applied to any signaling standard. Mostreaders are thought familiar with the Global System for Mobile (GSM)communications signaling standard. Those of ordinary skill in the art,however, also recognize that exemplary embodiments are equallyapplicable to any communications device utilizing the Time DivisionMultiple Access signaling standard, the Code Division Multiple Accesssignaling standard, the “dual-mode” GSM-ANSI Interoperability Team(GAIT) signaling standard, or any variant of the GSM/CDMA/TDMA signalingstandard. Exemplary embodiments may also be applied to other standards,such as the I.E.E.E. 802 family of standards, the Industrial,Scientific, and Medical band of the electromagnetic spectrum,BLUETOOTH®, and any other.

Exemplary embodiments may be physically embodied on or in acomputer-readable storage medium. This computer-readable medium, forexample, may include CD-ROM, DVD, tape, cassette, floppy disk, opticaldisk, memory card, memory drive, and large-capacity disks. Thiscomputer-readable medium, or media, could be distributed toend-subscribers, licensees, and assignees. A computer program productcomprises processor-executable instructions for conducting the duediligence 20 of mortgage documents, as the above paragraphs explained.

While the exemplary embodiments have been described with respect tovarious features, aspects, and embodiments, those skilled and unskilledin the art will recognize the exemplary embodiments are not so limited.Other variations, modifications, and alternative embodiments may be madewithout departing from the spirit and scope of the exemplaryembodiments.

1. A method of conducting a due diligence of an electronic mortgagedocument, the method comprising: receiving, by a hardware processor, adue diligence file associated with the electronic mortgage document;retrieving, by the hardware processor, electronic data associated withthe due diligence file, the electronic data representing a currentversion of the electronic mortgage document; hashing, by the hardwareprocessor, the electronic data representing the current version of theelectronic mortgage document using a cryptographic hashing algorithm togenerate a verification hash value; comparing, by the hardwareprocessor, the verification hash value generated by the hashing of theelectronic data representing the current version of the electronicmortgage document to a cryptographic audit key received via the duediligence file; and verifying, by the hardware processor, that thecurrent version of the electronic mortgage document is authentic inresponse to the verification hash value matching the cryptographic auditkey received via the due diligence file; wherein the due diligence ofthe electronic mortgage document is based on the cryptographic audit keyreceived via the due diligence file.
 2. The method of claim 1, furthercomprising distributing the cryptographic audit key via a blockchain. 3.The method of claim 1, further comprising distributing the verificationhash value via a blockchain.
 4. The method of claim 1, furthercomprising determining that the current version of the electronicmortgage document is inauthentic in response to the verification hashvalue failing to match the cryptographic audit key received via the duediligence file.
 5. The method of claim 1, further comprising retrievingmetadata from the due diligence file, the metadata associated with theelectronic mortgage document.
 6. The method of claim 5, furthercomprising generating a digital signature in response to the hashing ofthe metadata associated with the electronic mortgage document.
 7. Themethod of claim 6, further comprising comparing the digital signaturegenerated in response to the hashing of the metadata associated with theelectronic mortgage document to the cryptographic audit key received viathe due diligence file.
 8. A system, comprising: a hardware processor;and a memory device, the memory device storing instructions, theinstructions when executed causing the hardware processor to performoperations, the operations comprising: receiving a due diligence filefor a due diligence associated with an electronic mortgage document;retrieving a cryptographic audit key associated with the due diligencefile, the cryptographic audit key generated by hashing an originalversion of the electronic mortgage document using a cryptographichashing algorithm; retrieving a current version of the electronicmortgage document; hashing the current version of the electronicmortgage document using the cryptographic hashing algorithm to generatea verification hash value; comparing the verification hash valuegenerated by the hashing of the current version of the electronicmortgage document to the cryptographic audit key generated by thehashing the original version of the electronic mortgage document; anddetermining that the current version of the electronic mortgage documentis authentic in response to the verification hash value matching thecryptographic audit key; wherein the due diligence associated with theelectronic mortgage document is based on the cryptographic audit keyassociated with the due diligence file.
 9. The system of claim 8,wherein the operations further comprise distributing the cryptographicaudit key via a blockchain.
 10. The system of claim 8, wherein theoperations further comprise distributing the verification hash value viaa blockchain.
 11. The system of claim 8, wherein the operations furthercomprise determining that the current version of the electronic mortgagedocument is inauthentic in response to the verification hash valuefailing to match the cryptographic audit key.
 12. The system of claim 8,wherein the operations further comprise retrieving metadata from the duediligence file, the metadata associated with the electronic mortgagedocument.
 13. The system of claim 12, wherein the operations furthercomprise generating a digital signature in response to the hashing ofthe metadata associated with the electronic mortgage document.
 14. Thesystem of claim 13, wherein the operations further comprise comparingthe digital signature generated in response to the hashing of themetadata associated with the electronic mortgage document to thecryptographic audit key received via the due diligence file.
 15. Amemory device storing instructions that when executed cause a hardwareprocessor to perform operations, the operations comprising: hashingmetadata associated with an original version of an electronic mortgagedocument using a cryptographic hashing algorithm to generate acryptographic audit key; retrieving sourcing data associated with acurrent version of the electronic mortgage document, the sourcing dataidentifying a network location storing the current version of theelectronic mortgage document; hashing the sourcing data using thecryptographic hashing algorithm to generate a cryptographic source key;generating a due diligence file for a due diligence associated with theelectronic mortgage document, the due diligence file comprising thecryptographic audit key and the cryptographic source key; splitting thedue diligence file for the due diligence associated with the electronicmortgage document into multiple shares via a secret sharing algorithm;integrating the multiple shares split via the secret sharing algorithminto different blockchains; and publishing the different blockchains viathe Internet to an auditor for the due diligence associated with theelectronic mortgage document.
 16. The memory device of claim 15, whereinthe operations further comprise determining a minimum number of themultiple shares to be published per each one of the differentblockchains.
 17. The memory device of claim 15, wherein the operationsfurther comprise determining a number of the different blockchains basedon a total number of the multiple shares split via the secret sharingalgorithm.
 18. The memory device of claim 15, wherein the operationsfurther comprise determining a ratio based on a number of the differentblockchains and a total number of the multiple shares split via thesecret sharing algorithm.
 19. The memory device of claim 18, wherein theoperations further comprise determining a number of the differentblockchains based on a total number of recipients of the differentblockchains.
 20. The memory device of claim 17, wherein the operationsfurther comprise determining a ratio based on a number of the differentblockchains and a total number of recipients of the differentblockchains.